-
Notifications
You must be signed in to change notification settings - Fork 220
feat: customize mapping annotation in kubernetes dependent resource #2075
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
private boolean useDefaultAnnotationsToIdentifyPrimary() { | ||
return !(this instanceof SecondaryToPrimaryMapper) && !garbageCollected && isCreatable(); | ||
private boolean useAnnotationsToIdentifyPrimary() { | ||
return !garbageCollected && isCreatable(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why was the check on SecondToPrimaryMapper
implementation removed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(Made an improvement on naming.)
So it has now different definition a little, it is not just for the default annotation. Before it was using default annotation and that was checked. Now it check if it does not use owner reference for that.
Signed-off-by: Attila Mészáros <csviri@gmail.com>
Signed-off-by: Attila Mészáros <csviri@gmail.com>
Signed-off-by: Attila Mészáros <csviri@gmail.com>
54389d3
to
a060844
Compare
…2075) Signed-off-by: Attila Mészáros <csviri@gmail.com>
…2075) Signed-off-by: Attila Mészáros <csviri@gmail.com>
The implementation does not model very nicely the situation but makes it doable relatively easily.